r? @BoxyUwU

rustbot has assigned @BoxyUwU.
They will have a look at your PR within the next two weeks and either review your PR or reassign to another reviewer.

Use r? to explicitly pick a reviewer

These commits modify compiler targets.
(See the Target Tier Policy.)

Some changes occurred in src/doc/rustc/src/platform-support

cc @Noratrieb

The previous PR stalled out on concerns of ecosystem breakage, but see this comment for @est31 concluding we can move forward without further mitigation: #125692 (comment)

I would like to nominate this for FCP or whatever the current process is to land these kinds of major toolchain changes.

Landing this update is expected to resolve ongoing issues in the ecosystem with rootless docker images.

I've also drafted a rust-lang blogpost announcing this change (based on the previous musl update's post).

The process for bumping the target baseline of Tier 2 targets is currently a Major Change Proposal + FCP (see Changing target baseline (e.g. minimum Darwin or Windows version bump) part). If you draft an MCP, I'll help with the notifying relevant target maintainers part.

Changing target baseline (e.g. minimum Darwin or Windows version bump)

• Propose using: MCP
• Approve using: FCP
• Write an MCP describing why the target should have a change of baseline and once discussion has concluded, an FCP can be started to approve the change of baseline.

r? @wesleywiser (since you've reviewed the previous attempt)

I have filed an MCP:

• Upgrade *-linux-musl targets to musl 1.2.5 compiler-team#887

Building host compiler plus musl stds for crater run.

@bors try

⌛ Trying commit 1926e11 with merge 1271e16...

💥 Test timed out

A job failed! Check out the build log: (web) (plain)

@bors2 delegate=try

@bors2 try

⌛ Trying commit 1926e11 with merge c066bf6…

To cancel the try build, run the command @bors2 try cancel.

It's been so long my old friend... or perhaps the grandchild of my old friend......

For whatever reason, that timed out job built LLVM in 4 hours and 11 minutes, and when the dist toolchain build time (probably a bit more than 2 hours) is added on top, we hit the 6 hours job timeout limit.

(Discussed in #t-infra > molasses dist-x86_64-musl try-build)

☀️ Try build successful (CI)
Build commit: c066bf6 (c066bf6804adc55193b71afdff6a56922f4a8689, parent: 8de4c7234dd9b97c9d76b58671343fdbbc9a433e)

@craterbot run mode=build-and-test name=musl_upgrade_1_2_5_in_2025 start=try#8de4c7234dd9b97c9d76b58671343fdbbc9a433e+target=x86_64-unknown-linux-musl end=try#c066bf6804adc55193b71afdff6a56922f4a8689+target=x86_64-unknown-linux-musl

👌 Experiment musl_upgrade_1_2_5_in_2025 created and queued.
🔍 You can check out the queue and this experiment's details.

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

🚧 Experiment musl_upgrade_1_2_5_in_2025 is now running

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@craterbot abort

Yielding to #141588 (comment) which is time sensitive (needed for release later this week).

🗑️ Experiment musl_upgrade_1_2_5_in_2025 deleted!

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

@craterbot run mode=build-and-test name=musl_upgrade_1_2_5_in_2025-retry-1 start=try#8de4c7234dd9b97c9d76b58671343fdbbc9a433e+target=x86_64-unknown-linux-musl end=try#c066bf6804adc55193b71afdff6a56922f4a8689+target=x86_64-unknown-linux-musl

👌 Experiment musl_upgrade_1_2_5_in_2025-retry-1 created and queued.
🔍 You can check out the queue and this experiment's details.

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

🚧 Experiment musl_upgrade_1_2_5_in_2025-retry-1 is now running

ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

🎉 Experiment musl_upgrade_1_2_5_in_2025-retry-1 is completed!
📊 10093 regressed and 131 fixed (652296 total)
📰 Open the full report.

⚠️ If you notice any spurious failure please add them to the denylist!
ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more

Crater problem is known: #t-infra > crater: >100k "prepare-fail" crates?.

Link to prior run. Just looking at the numbers:

Assuming those 20% crates that we don't have results from have the same distribution of regressions (not sure that's how crater works!), we'd have 12111 regressed crates in total, or 1.8%. The 3% rise in the absolute number of regressions is probably within the error of that extrapolation method.

The number of total crates has risen by 35%. So one could say we outgrow the problem by just having the group of public projects grow :). Probably the earlier crater run already selected for the tail of projects that basically never do cargo update, given that back then the libc release had been out for almost a year already.

With the numbers of the earlier crater run we already said we are going to do the upgrade. I think these too should allow the same conclusion.

hmm, is there a patch or something we can apply while using crater to force-update the getrandom users? then we can retry just the regressions.